|
Component-oriented database (CODB) is a way of data administration and programming DBMS's using the paradigm of the component-orientation. ==Concepts== The paradigm of ''component-orientation'' (CO) is a development of the object-orientation (OO) in programming and data modeling, leading toward the extreme the possibilities of reuse. In this model type, classes are aggregate in cells called ''components'',〔 that execute a role similar to the function in the structured programming, a way of processing information contemporary to the relational database model. So the component-orientation mixes a set of features of its predecessor models. Understanding it is simpler while thinking of the ''visual component'', that is an application〔or even a small application or applet〕 which not being deployed into an executable or bytecode but otherwise turned to be linked by an icon inside another application, icon when one clicks on it implements certain tasks. Then this concepts can be extended to ''non-visual components''. In database activities, the component, visual or not, is an aggragate of ''classes'', in the sense of ''OO'', that can be linked to other ones by ''adapters''.〔(【引用サイトリンク】title=Components: Interfaces and Adapters )〕 As after the OO model conception data and code programming code are mixed in a cohesive body, there are some difficulties in conceiving where the ''CODB'' and ''CO'' programming are separate one from the other. Although this enigma is important in conceptual epistemological area, in practical data processing there isn't so importance in this question because of usage of mapping models to large scale used software, like the mappings called ''ORDBMS'' and ''CRDB'' (component-relational database), in which the separation of data and code are still well defined.〔(【引用サイトリンク】title=Introduction to Java in Oracle Database )〕 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Component-oriented database」の詳細全文を読む スポンサード リンク
|